sites now not responding on port 80 [closed]

Posted by JohnMerlino on Server Fault See other posts from Server Fault or by JohnMerlino
Published on 2012-12-10T21:47:27Z Indexed on 2012/12/10 23:06 UTC
Read the original article Hit count: 171

Filed under:
|

Possible Duplicate:
unable to connect site to different port

I was trying to resolve an issue with getting a site running on a different port:

unable to connect site to different port

But somehow it took out all my other sites. Now even the ones that were responding on port 80 are no longe responding, even though I did not touch the virtual hosts for them.

I get this message now:

Oops! Google Chrome could not connect to mysite.com

However, ping responds:

ping mysite.com PING mysite.com (64.135.12.134): 56 data bytes 64 bytes from 64.135.12.134: icmp_seq=0 ttl=49 time=20.839 ms 64 bytes from 64.135.12.134: icmp_seq=1 ttl=49 time=20.489 ms

The result of telnet:

$ telnet guarddoggps.com 80 Trying 64.135.12.134... telnet: connect to address 64.135.12.134: Connection refused telnet: Unable to connect to remote host

© Server Fault or respective owner

Related posts about apache2

Related posts about port